…ENTS.tape

Idempotent bash sweep — appends a one-line @x wilson_pool resource-
utilization pointer (→ ~/core/atlas/POOL.tape) right below the @v spec
entry of each ~/core/*/AGENTS.tape. Until wilson is the primary harness,
Claude Code CLI sessions read CLAUDE.md (→ AGENTS.tape) on project open;
this nudges every session toward host-pool resource utilization.

--commit flag commits each repo's AGENTS.tape in isolation
(git commit --only), guarded so a repo with pre-existing AGENTS.tape
changes is left as a working-tree edit, never swept into our commit.
Re-runnable when new repos appear.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@x wilson_pool / @x hexa_verify entries below the @v spec — nudge Claude
Code CLI / wilson sessions toward host-pool resource utilization and
verification-via-hexa-CLI for heavy / verification work. Mini-guides:
~/core/atlas/{POOL,VERIFY}.tape. Synced by wilson tools/agents-banner-sync.sh.

…er; add hexa_verify

Renamed tools/pool-banner-sync.sh → tools/agents-banner-sync.sh and
generalized from a single hardcoded entry to a BANNER_MARKERS /
BANNER_TEXT list — per-entry idempotent (a file keeps the entries it
already has; only missing ones are inserted). Banner now carries two
@x entries swept below the @v spec of every ~/core/*/AGENTS.tape:

  @x wilson_pool  → ~/core/atlas/POOL.tape   (host-pool resource use)
  @x hexa_verify  → ~/core/atlas/VERIFY.tape (verification via hexa CLI)

--commit guard generalized: commits only when the AGENTS.tape diff is
exactly our insertion (added == 4·entries-inserted, removed == 0) so a
repo with pre-existing AGENTS.tape edits is left as a working-tree edit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

pool_list's schema advertised {"json":{"type":"boolean"}} and the CLI
layer parsed `pool list --json` into args.json=true, but pool_invoke_list
only ever read args.fresh — the json param was dead. Added a want_json
branch to all four exit paths (cache-hit · hosts.json malformed · empty
roster · roster fallback) emitting json_stringify of the host data.

wilson test 23/23 PASS.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

A cache older than 1h (or missing probed_at) can have `reachable`
silently lie — e.g. the WireGuard mesh goes down after the probe, so
`pool list` keeps reporting a dead host as reachable and consumers
route work to it.

pool_invoke_list's cache path now computes age_sec from probed_at vs
timestamp() and flags stale=true past the 1h threshold. Human output
gains a `⚠ STALE cache` warning line + `age` in the header; --json
gains `stale` + `age_sec` fields (and metadata.stale).

Verified: forged-old cache → ⚠ + stale:true; fresh cache → no warning.
wilson test 23/23 PASS.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>